Overview of Connecting Related Data

In modern database systems, information is rarely kept in a single giant spreadsheet. Instead, Relational Databases organize data across multiple separate, logically connected tables. By breaking data down into distinct subjects—such as customers and purchases—systems eliminate repetitive entries and maintain high accuracy while still letting users pull together complete reports.

Core Concepts of Relational Linking

Table Separation: Isolating distinct entities (such as customers, products, and orders) into dedicated tables prevents data duplication.
Data Integrity: Storing information in a single authoritative place ensures that updates (like changing a shipping address) only need to happen once.
Secure References: Tables point to one another using unique identifiers, allowing database queries to easily assemble complete reports without repeating records.

QUESTION 1

What is the primary benefit of organizing data into separate, connected tables instead of a single massive spreadsheet?

Making file sizes larger and harder to manage

Forcing users to type customer names repeatedly

Eliminating data redundancy and improving accuracy

Storing all information in random order

QUESTION 2

In a relational database, how are two related tables (such as Customers and Orders) typically linked together?

Copying and pasting customer info into every order row

Sorting both spreadsheets alphabetically by date

Renaming the files to match each other

Using a shared unique identifier like a Customer ID

QUESTION 3

What happens when a customer updates their shipping address in a properly normalized relational database?

The address is updated in one single place in the Customers table

The database deletes all historical order records

Every past order must be manually edited to match

Nothing happens because addresses cannot be changed

QUESTION 4

Which of the following best describes data redundancy in spreadsheets?

Organizing backups on external hard drives

Storing data securely in an encrypted vault

Repeating the same information multiple times across rows and columns

Linking separate tables with foreign keys

QUESTION 5

Why do relational database management systems use distinct subjects for tables?

To eliminate the need for computer processors

To keep data modular, organized, and easy to query comprehensively

To slow down data retrieval for security purposes

To ensure users can only ever view one row at a time

Case Study: Online Store Database Design

Analyze the database architecture for an e-commerce platform.

An online bookstore currently records every purchase in a single massive spreadsheet. Every time a customer places an order, their name, email, home address, and phone number are re-typed alongside the book title and price. Management wants to transition to a relational database.

1. What problems does the current single-spreadsheet approach cause when a customer changes their phone number or address?

Answer:
It causes data redundancy and a high risk of typos or inconsistencies, because the change would have to be manually tracked and updated across dozens or hundreds of previous order rows.

2. How should the database be restructured into separate tables to solve this issue?

Answer:
By separating data into a 'Customers' table (holding unique customer details and a Customer ID) and an 'Orders' table (holding order specifics and referencing the Customer ID), ensuring customer updates only happen in one place.